Search Results: "mace"

1 December 2011

Christian Perrier: Between 60 and 64 languages supported in Debian Installer

(including English!) The string freeze of Debian Installer officially ended at 23:59 yesterday (Sept. 20th). Indeed, this was extended a bit to today, with agreement by Otavio Salvador who I thank for this. That allowed Zak to "save" Tagalog and also the Welsh and Latvian translators to polish their work. We now have to decide about some of these languages: those that failed to meet the release criteria but were formerly activated in D-I. There are four such languages: Amharic, Welsh, Estonian and Northern Sami. Please find below the mail I just sent to debian-i18n and debian-boot. I promised that this discussion would happen in public. It will (but it will be short as we can't delay the release of the installer for ages....and I think that my proposals are reasonable!)
First of all, the numbers as of Sunday Sept. 21st 09:32 UTC (date of
the last commit with an l10n update):
Languages meeting the release criteria: 59
------------------------------------------
Already activated and complete for level 1: 51
 Arabic, Belarusian, Bulgarian, Bosnian, Catalan, Czech, Danish,
 German, Dzongkha, Greek, Esperanto, Spanish, Basque, Finnish, French,
 Galician, Gujarati, Hebrew, Hindi, Croatian, Hungarian, Indonesian,
 Italian, Japanese, Georgian, Khmer, Korean, Lithuanian, Latvian,
 Macedonian, Malayalam, Marathi, Norwegian Bokm l, Nepali, Dutch,
 Norwegian Nynorsk, Punjabi, Polish, Portuguese, Brazilian Portuguese,
 Romanian, Russian, Slovak, Albabian, Swedish, Tamil, Thai, Turkish,
 Vietnamese, Simplified Chinese, Traditional Chinese
Already activated and complete for sublevels 1 and 2: 6
Bengali, Kurdish, Slovenian, Tagalog, Ukrainian, Wolof
Not yet activated languages complete for sublevels 1 and 2: 2
 (the mail in -i18n and -boot says 3 but this is an error by me)
Irish, Serbian
Languages failing to meet the release criteria: 15
--------------------------------------------------
Activated languages: 4
Amharic, Welsh, Estonian, Northern Sami
Not yet activated languages: 11
Afrikaans, Persian, Armenian, Icelandic, Kazakh, Kannada,
Malagasy, Malay, Telugu, Urdu, Xhosa
Discussion
----------
(careful people will notice that I moved Welsh down to "failed to meet
the release criteria" as this is what is technically correct)
Nothing to discuss for the 57 already activated languages that meet
the defined criteria. They'll be kept or first activated in the RC1
release of Debian Installer.
Similarly, nothing to discuss for the 11 languages that were not
activated and haven't made it. They will remain unactivated.
Two languages should be activated as they have met the release
criteria for the first time during the string freeze: Irish and Serbian.
This adds more load (and size changes) to D-I but I really don't see
any reason to not follow our own rules there.
The discussion comes for the 4 languages that fail to meet the release
criteria. Here are my proposals with some rationale:
Amharic: 
  I would really dislike deactivating Amharic because it's highly
  symbolic to have the language of Ethiopia activated. We have so few
  African languages. Also, the translation is nearly complete and the
  translator was well coping with updates until July. The missing
  stuff for Amharic in sublevels 1 and 2 are messages about loading
  drivers or firmware from removable media, the rescue mode stuff for
  the graphical installer and some messages that briefly appear during
  finish-install. A little bit more important is the message warning
  that the boot partition is not ext2 or ext3, added in August by
  tbm. I think this is not enough to drop out one year of efforts for
  the translator
  As a consequence, I propose to KEEP Amharic.
Welsh:
  Only five strings are missing in sublevels 1 and 2 because of the
  small experience of PO files by the person who completed the
  translation during last week. One will make the regular user login
  name screen to be in English and others will make the GRUB password
  screen to be in English as well, that's all.
  Additionnally, we can safely assume that all potential users of
  Welsh have good skills in English...and will therefore very easily
  cope with these screens.
  As a consequence, I propose to KEEP Welsh.
Estonian:
  The translation had NO update since Etch. The last update is dated
  back to Feb. 17th 2007. I haven't got any sign of life from the
  translator and no Estonian users have volunteered to maintain the
  translation.
  Missing strings are in many places, including several screens that
  appear in default installs. Even though one can assume that the
  skills of the average Linux user in Estonia is fairly good, I think
  this is not enough to throw users in a big mix of English and
  Estonian.
  As a consequence, I propose to DROP Estonian.
Northern Sami:
  The translation is very incomplete. With about any other language,
  that would be a reason to drop the translation.
  However, a few reasons make me suggest keeping it:
   - Northern Sami is mostly used in Norway and D-I will fall back
     to Norwegian Bokm l which is understood by all potentials users
     as it is teached in all Norwegian schools. 
   - Users will be warned, *in Sami*, about this situation
   - The choice of Sami will be kept in localechooser even if the
     translations are dropped. This is on request of Debian Edu
     developers to avoid them to develop a special boot floppy
     to offer the choice of Sami (a requirement for Norwegian
     schools). I personnally think this is a reward to Debian Edu and
     its ancestor Skolelinux for their initial involvement in the
     development of D-I
  As a consequence, I propose to KEEP Northern Sami.
I understand that these choices may be debatable and some may sound
slightly subjective. I however think this is the best way to be fair
with translators' efforts without compromising the quality of D-I.
Please note that the final word on this will be by D-I release
managers...but advices are very much welcomed.

29 November 2011

Lior Kaplan: Translation status for LibreOffice 3.5.0 beta0

Following the good examples of Christian Perrier (Debian l10n leader), I m glad to publish translation status update for LibreOffice 3.5.0 beta0. Information is based on the documentation foundation pootle server. 9 languages at 100%: Catalan (ca), Danish (da), French (fr), Scottish Gaelic (gd), Portuguese (pt), Portuguese (Brazil) (pt_BR), Russian (ru), Slovenian (sl) and Chinese (China) (zh_CN). 15 languages at 99%: Asturian (ast), Bulgarian (bg), Breton (br), Welsh (cy), Belarusian (be), German (de), English (United Kingdom) (en_GB), Esperanto (eo), Estonian (et), Galician (gl), Latvian (lv), Norwegian Bokm l (nb), Polish (pl), Turkish (tr) and Slovak (sk). 1 languages at 98%: Hungarian (hu) 15 languages at 97%: Assamese (as), Czech (cs), Chinese (Taiwan) (ch_TW), Spanish (es), Basque (eu), Finnish (fi), Irish (ga), Gujarati (gu), Croatian (hr), Italian (it), Icelandic (is), Kannada (kn), Marathi (mr), Dutch (nl) andTelugu (te). 2 languages at 96%: Hebrew (he) and Japanese (ja). 1 languages at 95%: Vietnamese (vi) 5 languages at 94%: English (South Africa) (en_ZA), Indonesian (id), Khmer (km), Tamil (ta) and Uighur (ug). 4 languages at 93%: Arabic (ar), Bengali (bn), Catalan (Valencia) (ca_XV) and Korean (ko). 1 languages at 92%: Oriya (or). 1 languages at 91%: Swedish (sv). 1 languages at 90%: Greek (el). 11 languages between 80%-89%: Afrikaans (af), Bosnian (bs), Hindi (hi), Lithuanian (lt), Macedonian (mk), Burmese (my), Norwegian Nynorsk (nn), Occitan (oc), Oromo (om), Sinhala (si) and Ukrainian (uk). 11 languages between 70%-79%: (no list) 10 languages between 60%-69%: (no list) 13 languages between 50%-59%: (no list)
Filed under: LibreOffice

26 February 2011

Neil Williams: Why software patents differ from pharmaceutical patents

I was going to make this a comment against Ritesh Raj Sarraf's post about patents and pharmaceuticals but the comment got way too long.

The basic problem is that patents on pharmaceuticals cannot be directly compared to patents on software and the explanation gets a bit involved. It's worse than apples and oranges, it's more like comparing an algorithm to a piece of DNA.

Patented pharmaceuticals must declare the precise chemical formula of the molecule (and a whole lot else besides) before the molecule can be brought to market but the company holding the patent is legally prevented from protecting themselves against slightly different molecules which are blatantly based on the protected molecule. All modification results in a new patentable product, legally separated from the original.

Therefore, the first company to patent a molecule from a new class is instantly joined in the field by other companies who are (obviously) watching the research news channels very carefully. (In their shoes, you would do the same or you go bust.) These companies simply add a flourine ion or change a hydrogen to a hydroxl group or any other number of minor, apparently inconsequential, changes. Changes which, in software, would be deemed a derivative work and would be roughly equivalent to changing a single local variable from a 16bit integer to a 32bit integer in a single function in a single file in the entire codebase. i.e. a trivial bug fix or even a typo.

A molecule with a couple of hundred atoms can have a change affecting one atom and be a completely new patentable item without any risk of the other company being sued for patent infringement, plagiarism, copyright violation (there is no copyright) or any other barrier. It's common to find that molecule foo is joined on the market by a desoxyfoo and a flourofoo etc. with a chlorofoo just around the corner, within months of the class-leader being launched. It can't be compared to software - effectively, every new release gets a new patent which covers the entirety of everything contained in that release, even if 99.999999999% of it is precisely the same as is covered under other several other patents held by extremely litigious competitors.

Modification is simply not prohibited - copying without making any changes whatsoever to the active molecule is prohibited. Changes to the inactive ingredients will be prosecuted - changes to the active ingredient will not. Comparing this with software is likely to drive you insane.

For example, the mere process of packaging an upstream release for a distribution would be patent infringement in pharmaceutical terms - UNLESS you deliberately patch the original source to make an utterly trivial and apparently pointless change. At that point, the upstream completely disown your entire release and you would have to fix every bug yourself - without the original upstream even telling you whether they fixed the same bug themselves, because they aren't ABLE to modify the upstream code without starting a whole new project and they won't tell you why or how they changed things. There is no such thing as an alpha-release of a molecule. Every release is final and no subsequent modification is possible - unless it only affects the inactive ingredients, e.g. by adding a slow release coating. These changes can affect the way that the molecule acts on the test subject / patient but must not change the active ingredient itself in any identifiable way. So the upstream can make a new wrapper (new packaging) but nobody else is allowed to do so until the patent expires. Once the patent expires, every one and their dog is allowed to make identical copies of the active ingredient in their own inactive packaging and these are called generics. Generics still need testing to ensure that the active ingredient truly is the same and that the generic behaves in the same way as the original but this process is cheaper than making a change to the active molecule.

A changed active molecule is an entirely new substance, it gets a new patent and it needs to go through largely the same amount of testing as the patented original but the new company still gets a head start on what the molecule is likely to do and what side-effects (by now noticeable with the class-leader product which is in large scale trials or even on the market) would be harmful to the future usefulness of their new, derivative, molecule. The new company simply jumps onto the bandwagon shouting "I want a piece of that action!" and there is absolutely nothing the original company can do about it, except try to show that their original molecule is better than the new competitors and to try and build a substantial market share before everyone switches to the new derivative. (Prescribers are human and tend therefore to be lazy, so unless there's a reason to change, the class leader will still have substantial share even after several derivatives exist.)

It's an arms race - each company tries to create as many of these potential "me-too" variants as possible in-house, put as many as can be (financially) supported through trials, keep pursuing those which don't have prohibitive side-effects / problems in tests and hope that, at the end, one of their versions will actually turn out to have better effectiveness or fewer side-effects. If not, they just have to market one as "as-effective-and-no-more-harmful-but-CHEAPER-than" the class leader. The majority of "me-too" molecules come under this category - even if the company concerned would try to point to infinitesimal differences in trial data to pretend otherwise. All this with the knowledge that the very hour that the patent expires, a dozen generic manufacturers will flood the market with copies which do not need to recover the massive costs of the original research and are therefore massively cheaper.

How much cheaper? patented molecules may cost 30 for 28 doses on Monday and one generic may cost 3p for 500, another may cost 40p for 10,000 on Tuesday, the day after the patent expiry. Generic houses only need to cover the actual costs of manufacture, not the costs of the original patent etc. and by the time the patent expires, the efforts of the patent holder to generate market share mean that economies of scale become evident. The absolute cheapest isn't necessarily the one who gets the contract either, these things all have expiry dates and all 10,000 have to be sold / supplied from a single location within that date to actually deliver the full savings. So then you get satellite generics who buy in quantities of a few million and pack down into 56 or less so that the total purchased quantity can sit on many shelves instead of just one. It's the same tablet in the end, with the same markings too. All that differs is the marking on the foil and the colour of the cardboard. (Oh and the same foil and colour cardboard can contain tablets with different markings from different manufacturers from one batch to the next, all within the branding of the same repackaging company.)

The original patent-holding company also has an interest in generating their own "me-too" derivatives, sometimes marketed under the name of a company which turns out to be solely owned by the parent of the original company. It can get horribly recursive.
Sometimes, the derivative from the sibling company hits the market before the "true" competitor from a different company - simply because all companies try to have many molecules in development at any one time (because most changed molecules fail in testing) and sometimes they get lucky and come up with two v.similar molecules and have to do something to justify the cost of developing both. That can turn out to be a poisoned chalice rather than two golden geese.

Sometimes, the company fails to get enough variants through testing and the company then gets bought out by a rival - who then gains their research and continues experimenting with other derivative molecules based on the ones already tested and dismissed. The limiting factor is the money.

At this point, I must now declare my cards. I used to be a pharmacist and although I am still entitled to call myself the holder of a Batchelor of Sciences degree in Pharmaceutical Sciences I am most definitely no longer a pharmacist. I therefore defer to my still-registered colleagues in case I've messed up any of the detail here. The above cannot be declared as the opinion of a pharmacist. I am an ex-pharmacist who voluntarily chose to resign his registration to take up full time work as a software developer rather than pay the exorbitant costs of maintaining such registration and all the "proof-of-competency" requirements which such registration requires.

Finally, before you ask, I am very happy to be an ex-pharmacist - my erstwhile colleagues have my ongoing sympathy but no matter how much some of them may beg, they all know that I will not be rejoining them on that side of the dispensary bench if I've got any choice in the matter.

Software is just better. It's all just recycled electrons.

Ritesh Raj Sarraf: Patents and the Pharmacy Industry

Mosf of us would be well versed with the Patent system in general. We have patents in every sector - Technology, Agriculture, Pharmacy etc. Most readers in our profession must already be well versed of the Pros/Cons of the Patent system in Software/Technology. Patents in software are more like ammunition. The more you have, the stronger you are. We don't seem much cat fight in Software/Technology because not one organization own all the patents for a product. An IBM ThinkPad might be using a cool track pad feature which might be a patent of Dell. Since the finished product comprises of many patents from different owners in the same industry, it is better to play good with each other. You scratch my back, I scratch yours. But what about the Pharmaceutical Industry? There, one single patent could comprise the product. I was reading this document from Bruce Lehman which touches upon Patents and Pharmaceutical Industries, but couldn't find an answer to my question. read more

19 December 2010

Gintautas Miliauskas: Mobile App Camp

On the last weekend my team and I participated in the Mobile App Camp (link in Lithuanian) organized by Omnitel, which is one of the dominant mobile operators in Lithuania. The event seems to be part of Omnitel's push for increasing the share of smartphones in the Lithuanian market, which has been lagging behind the European trends.

Our team consisted of Povilas Kytra, who is behind the TV.LT project, Mantas Kanaporis from A-Gain and me. In the weekend we built an app that shows the TV programme for the coming day for all the Lithuanian TV channels. (The app is not yet available on the Android Market, but we are working on it.)

Here's a screenshot of the main screen of the application:


The app was built using the standard Android Development Toolkit on Eclipse. The app gets the content from a Rails-based server containing a simple database and couple JSON views.

I had some experience of developing for Android before, but it was mostly about working with graphics on canvas, while in this app we used some standard GUI controls (with some nifty styling).

For the source control, we used a private repository on bitbucket.org. That one was a huge letdown: a 'hg push' or 'hg pull' would take ages (or at least that's how it seemed to me in comparison to GitHub), and we had no end of trouble with merging, partly due to the number of commands needed to get the repositories in sync (hg pull; hg update; hg merge; hg commit; hg push). Even Subversion would probably have worked better.

The event itself was great fun. It had been a while since I had last coded intensively for the entire weekend. There were quite a few decent ideas presented by the participants, and some of them were successfully implemented.

The rating system was somewhat disappointing though. The event was supposed to be a contest, with four predefined criteria for winning apps (still available on the website): uniqueness in the Lithuanian market, magnitude of the target group, value provided to the user and creativity. In the end, however, the jury nominated apps for three different awards (best app built on an existing database, best app built anew, and the "hope" nomination) with one app awarded from each category. Our app scored second in the first nomination, so we did not get an award, even though we would probably have been in the global top three, were the original criteria upheld.

To be fair, we did not stand much chance against the winner in our category, an app based on vaistai.lt, which sported a database of pharmaceuticals with detailed usage instructions, information about drug stores in Lithuania with maps and inventory status, and even a barcode scanner. Hats off to them. Another winner was "Alaus radaras" ("Beer radar") with locations of local beer bars and inventory info. The third one was "3 milijonai teis j " (Three million judges"), which, as far as I understood, was a conception for a basketball-throwing game (basketball is very big in Lithuania, it is a second national religion).

To conclude, it was a fun event and I wish we will be having more of those in Vilnius, even though the Monday after the long weekend was very unproductive.

3 December 2010

Thijs Kinkhorst: Federated access to a wiki with simpleSAMLphp and Dokuwiki

If you want to provide a wiki but want to leave the authentication to one or more external identity providers, like an identity federation, Dokuwiki and simpleSAMLphp are a good combination. However, the existing documentation is lagging behind on developments in these software packages (i.e. doesn't work anymore), so here's what worked for me. Ingredients:
A Debian 5.0 Lenny system.
Dokuwiki Debian Lenny package (0.0.20080505-4+lenny1).
simpleSAMLphp Debian squeeze package (1.6.2-1).
SSP is not available in Lenny yet but the package from Squeeze installs cleanly on Lenny.
simpleSAMLdokuwiki integration package.
Note that I'm linking to a bug report - you need the file version included in the bottom of that bug report, because the released versions are outdated.
I assume you have read the Dokuwiki and simpleSAMLphp documentation for information on how to install and configure either one; this article purely focuses on the integration part; not on e.g. how to connect an IdP to simpleSAMLphp. I also provided a patch to the simplesamldokuwiki class cited above to enable the IdP to not pass a 'mail' attribute: see bug report.

19 July 2010

Christian Perrier: Debian Installer final localization stats for upcoming squeeze beta1

After a quite long string freeze and last minute efforts by translators, I finally stopped the clock on Sunday July 11th for D-I localization update meant for the release of the beta1 version of debian-installer for squeeze. We finally have 65 supported languages. In a final effort, Belarusian, Ukrainian, Hungarian, Tagalog, Kurdish, Croatian and Macedonian were "rescued" and completed enough for being included in the release. Unfortunately, I had to deactivate Wolof, Serbian and Welsh because of lack of activity. For Serbian, this is very infortunate as new translators indeed tried to contact me with updates, which I missed and discovered only after it wasn't possible to revert the change. Good news are that Serbian is now already reactivated for the next release and we will even have both the Cyrillic and Latin versions of it. The mass upload of D-I packages happened mostly on Sunday 12th (you probably noticed that if you follow debian-devel-changes). It is already possible to test what will be D-I beta1: just go to the D-I development web page, then choose to download the daily built netboot image. Boot it with "install mirror/suite=unstable". This is not *exactly* what beta1 will give as this will install unstable and not testing, for non D-I packages...but I think that, until D-I packages migrate to testing, this is the best way to test beta1. The next step in D-I release preparation should be the mass migration to testing of most udeb packages.

1 July 2010

Christian Perrier: Care about D-I translation in your language?

If you do, then please read the current status of D-I localization, 3 days before the official end of the string freeze. You should do it particularly if you care about Belarusian, Ukrainian, Hungarian, Tagalog, Kurdish, Croatian, Macedonian, Wolof, Serbian, Welsh. (Brazilian Portuguese was also mentioned in that post but updates happened today and I'm confident that Felipe will soon catchup. Croatian is also likely to be OK as Josip is often updating at the last minute...).

7 May 2009

Biella Coleman: Go Elsevier

It looks like publishing fake journals was becoming closer to habit for Elsevir rather than a one-time exceptional mistake.
Scientific publishing giant Elsevier put out a total of six publications between 2000 and 2005 that were sponsored by unnamed pharmaceutical companies and looked like peer reviewed medical journals, but did not disclose sponsorship, the company has admitted. Elsevier is conducting an internal review of its publishing practices after allegations came to light that the company produced a pharmaceutical company-funded publication in the early 2000s without disclosing that the journal was corporate sponsored.
I really hope people use this an an opportunity to detach fully from them.

Biella Coleman: Go Elsevier

It looks like publishing fake journals was becoming closer to habit for Elsevir rather than a one-time exceptional mistake.
Scientific publishing giant Elsevier put out a total of six publications between 2000 and 2005 that were sponsored by unnamed pharmaceutical companies and looked like peer reviewed medical journals, but did not disclose sponsorship, the company has admitted. Elsevier is conducting an internal review of its publishing practices after allegations came to light that the company produced a pharmaceutical company-funded publication in the early 2000s without disclosing that the journal was corporate sponsored.
I really hope people use this an an opportunity to detach fully from them.

9 March 2009

Pablo Lorenzzoni: Maceio - took some days off

I finally took some days off. Those are most needed, since I spent carnival on call at the hospital (argh!)... So Brenda and I decided to spend those days at Maceio, capital of Alagoas state, and a very anticipated vacation. They have a lot of sun and beautiful beaches, enough to fill our week (and get some tan also). This picture was taken at Praia do Gunga (Gunga s Beach), a charming place with a calm shore, almost like a pool, protected by natural reefs. As you can see, I am having a bad time right now :-) Food is excellent, so are the people. But there are some inconveniences (as always). Beaches around downtown are not proper for bathing They re fighting a long fight against pollution (and loosing, if you ask me)... Also, Alagoas is a poor state Our guide said alphabetization covers less than 70% of the people Also, network connection is expensive in hotels. Ours charges BRL 1,00 every 5 minutes! And the speed is not the best. They have one of those systems requiring a web authentication before you go. I ve seem people complaining about this kind of system in Planet Debian before (reference please!) and suggesting Tunneling over DNS as a fix . I ve noticed it would work in our hotel, but I decided to try another approach I ve already written about: just a quick tunnel over an ssh connection. I know I told you I needed an authentication before, but that is for the first connection! Yes, once the connection is established, I could just log out (thus stop the charging). No new connections could be made, but the tunnel was already up, so just put everything through the tunnel and I should be fine right? Wrong. I got bitten by a drawback of the technique already pointed in a comment when I first wrote about it: in an error-prone network, TCP-in-TCP slowly dies of attempting to correct itself over and over and I was using a poorly connected wi-fi (loosing almost 30% of the packets!). So, I was left with the set-up of a not foreseen tunnel using DNS as the only option This would take time (and money)... So I decided for a simpler approach: SOCKS proxy. Yes, everything I would do could be done through a SOCKS! So a simple:

bash$ ssh -D 8888 my.remote.location
was all that I needed. That and setting my Firefox to use a SOCKS proxy on localhost:8888 and all went fine. I paid to set-up the tunnel then, once established, I logged out and kept using my tunnel all this time. Simple and effective, and I got some time left to blog about it. :-)

21 September 2008

Christian Perrier: The final count is 63

After a short discussion time, my proposals have been ACK'ed and we will have 63 languages supported, including English, in Debian Installer for Lenny. Etch had 58 supported languages. The final winners are (alphabetical order of ISO code): Amharic, Arabic, Belarusian, Bulgarian, Bengali, Bosnian, Catalan, Czech, Welsh, Danish, German, Dzongkha, Greek, English, Esperanto, Spanish, Basque, Finnish, French, Irish, Galician, Gujarati, Hebrew, Hindi, Croatian, Hungarian, Indonesian, Italian, Japanese, Georgian, Khmer, Korean, Kurdish, Lithuanian, Latvian, Macedonian, Malayalam, Marathi, Norwegian Bokm l, Nepali, Dutch, Norwegian Nynorsk, Punjabi, Polish, Portuguese, Brazilian Portuguese, Romanian, Russian, Northern Sami, Slovak, Slovenian, Albabian, Serbian, Swedish, Tamil, Thai, Tagalog, Turkish, Ukrainian, Vietnamese, Wolof, Simplified Chinese, Traditional Chinese Newcomers for Lenny are: Amharic, Welsh (back), Irish, Marathi, Northern Sami, Serbian We lost Estonian which was in Etch. Those that missed the deadline are of course all other languages of the world. We will put focus on languages where an effort started at some moment but could not be complete enough: Afrikaans, Estonian, Persian, Armenian, Icelandic, Kazakh, Kannada, Kashmiri, Lao, Malagasy, Malay, Sanskrit, Secwepemctsin, Telugu, Urdu, Xhosa Many thanks to all translators for this final effort. Thanks also to all people who urgently popped up last week to complete the translations for languages that were "orphaned". I hope this will bring us more translators...:-) I keep special thanks to Frans Pop here. He is, along with me, the author of the code that allows us to split D-I translations in "sublevels", allowing translators to focus on the most "important" messages. He also implemented prior warnings when users pick up a language where some less important screens aren't translated. This also allows us to more easily keep partly complete translations, or activate languages earlier. Without this, 11 languages should have been dropped.

Christian Perrier: Between 60 and 64 languages supported in Debian Installer

(including English!) The string freeze of Debian Installer officially ended at 23:59 yesterday (Sept. 20th). Indeed, this was extended a bit to today, with agreement by Otavio Salvador who I thank for this. That allowed Zak to "save" Tagalog and also the Welsh and Latvian translators to polish their work. We now have to decide about some of these languages: those that failed to meet the release criteria but were formerly activated in D-I. There are four such languages: Amharic, Welsh, Estonian and Northern Sami. Please find below the mail I just sent to debian-i18n and debian-boot. I promised that this discussion would happen in public. It will (but it will be short as we can't delay the release of the installer for ages....and I think that my proposals are reasonable!)
First of all, the numbers as of Sunday Sept. 21st 09:32 UTC (date of
the last commit with an l10n update):
Languages meeting the release criteria: 59
------------------------------------------
Already activated and complete for level 1: 51
 Arabic, Belarusian, Bulgarian, Bosnian, Catalan, Czech, Danish,
 German, Dzongkha, Greek, Esperanto, Spanish, Basque, Finnish, French,
 Galician, Gujarati, Hebrew, Hindi, Croatian, Hungarian, Indonesian,
 Italian, Japanese, Georgian, Khmer, Korean, Lithuanian, Latvian,
 Macedonian, Malayalam, Marathi, Norwegian Bokm l, Nepali, Dutch,
 Norwegian Nynorsk, Punjabi, Polish, Portuguese, Brazilian Portuguese,
 Romanian, Russian, Slovak, Albabian, Swedish, Tamil, Thai, Turkish,
 Vietnamese, Simplified Chinese, Traditional Chinese
Already activated and complete for sublevels 1 and 2: 6
Bengali, Kurdish, Slovenian, Tagalog, Ukrainian, Wolof
Not yet activated languages complete for sublevels 1 and 2: 2
 (the mail in -i18n and -boot says 3 but this is an error by me)
Irish, Serbian
Languages failing to meet the release criteria: 15
--------------------------------------------------
Activated languages: 4
Amharic, Welsh, Estonian, Northern Sami
Not yet activated languages: 11
Afrikaans, Persian, Armenian, Icelandic, Kazakh, Kannada,
Malagasy, Malay, Telugu, Urdu, Xhosa
Discussion
----------
(careful people will notice that I moved Welsh down to "failed to meet
the release criteria" as this is what is technically correct)
Nothing to discuss for the 57 already activated languages that meet
the defined criteria. They'll be kept or first activated in the RC1
release of Debian Installer.
Similarly, nothing to discuss for the 11 languages that were not
activated and haven't made it. They will remain unactivated.
Two languages should be activated as they have met the release
criteria for the first time during the string freeze: Irish and Serbian.
This adds more load (and size changes) to D-I but I really don't see
any reason to not follow our own rules there.
The discussion comes for the 4 languages that fail to meet the release
criteria. Here are my proposals with some rationale:
Amharic: 
  I would really dislike deactivating Amharic because it's highly
  symbolic to have the language of Ethiopia activated. We have so few
  African languages. Also, the translation is nearly complete and the
  translator was well coping with updates until July. The missing
  stuff for Amharic in sublevels 1 and 2 are messages about loading
  drivers or firmware from removable media, the rescue mode stuff for
  the graphical installer and some messages that briefly appear during
  finish-install. A little bit more important is the message warning
  that the boot partition is not ext2 or ext3, added in August by
  tbm. I think this is not enough to drop out one year of efforts for
  the translator
  As a consequence, I propose to KEEP Amharic.
Welsh:
  Only five strings are missing in sublevels 1 and 2 because of the
  small experience of PO files by the person who completed the
  translation during last week. One will make the regular user login
  name screen to be in English and others will make the GRUB password
  screen to be in English as well, that's all.
  Additionnally, we can safely assume that all potential users of
  Welsh have good skills in English...and will therefore very easily
  cope with these screens.
  As a consequence, I propose to KEEP Welsh.
Estonian:
  The translation had NO update since Etch. The last update is dated
  back to Feb. 17th 2007. I haven't got any sign of life from the
  translator and no Estonian users have volunteered to maintain the
  translation.
  Missing strings are in many places, including several screens that
  appear in default installs. Even though one can assume that the
  skills of the average Linux user in Estonia is fairly good, I think
  this is not enough to throw users in a big mix of English and
  Estonian.
  As a consequence, I propose to DROP Estonian.
Northern Sami:
  The translation is very incomplete. With about any other language,
  that would be a reason to drop the translation.
  However, a few reasons make me suggest keeping it:
   - Northern Sami is mostly used in Norway and D-I will fall back
     to Norwegian Bokm l which is understood by all potentials users
     as it is teached in all Norwegian schools. 
   - Users will be warned, *in Sami*, about this situation
   - The choice of Sami will be kept in localechooser even if the
     translations are dropped. This is on request of Debian Edu
     developers to avoid them to develop a special boot floppy
     to offer the choice of Sami (a requirement for Norwegian
     schools). I personnally think this is a reward to Debian Edu and
     its ancestor Skolelinux for their initial involvement in the
     development of D-I
  As a consequence, I propose to KEEP Northern Sami.
I understand that these choices may be debatable and some may sound
slightly subjective. I however think this is the best way to be fair
with translators' efforts without compromising the quality of D-I.
Please note that the final word on this will be by D-I release
managers...but advices are very much welcomed.

19 September 2008

Christian Perrier: More "saved" languages

This is now the last day of D-I string freeze and the suspense continues... Latvian has just been completed by Aigars: saved Albanian has been completed by Elian Myftiu who came back at the last minute (I have no other contact for that language): saved Serbian, which was very close to be activated last weeks finally got completed by Veselin Mijuskovic Welsh Linux users are attempting to requalify the language (it was de-activated in Etch) by using local language specialists apparently. As a consequence, we now have only 5 languages "in danger": Amharic, Estonian, Macedonian, Northern Sami and tagalog.

Christian Perrier: D-I l10n: the last minute rush

Hectic days... The last l10n teams are waking up and alarming messages seem to be sent in various places after my various blog posts, messages to lists, private messages, etc. (I think that the only place where I haven't yelled out for D-I translations is the street I live in). As of now, 7 languages are still in danger to be de-activated: Amharic, Estonian, Latvian, Macedonian, Northern Sami, Albanian, Tagalog Among these, Latvian and Macedonian should make it: Arangel Angov for Macedonian and Aigars Mahinovs for Latvian will probably complete the required minimum. For others, I'm afraid that Estonian, Albanian and maybe Tagalog will be deactivated. I have to think about it. I will be very sad for all of them if I have to do it. But I haven't got news from these translators for ages and I haven't been able to find any possible backup translator. For Albanian and Tagalog, that's not a surprise. For Estonian, I call this very disappointing. Northern Sami is a special case: this is the language of the Sami people in Norway, teached there in schools and important for DebianEdu...which originated in Norway and has been the pilar of D-I development a few years ago. As finding Sami translators is very difficult, I will probably keep the language (also, because it has a solid backup with Norwegian). Amharic is also special for me. The l10n effort is very specific: the translator works on ships all around the world, from his words, and can only communicate with me when he reaches a harbour. He has also been very committed to reach completeness (which he did) and the translation was only fuzzied by last minute changes in August. I'll probably fight to keep that language in D-I..:-) Still, there's one day left. So if your language is not 100% on D-I statistics for level 1, then try to do something. And, guess what? After the deadline is reached, I'll still have work to do: get as many levels 2-5 translations completed. All of these belong to regular Debian packages so they're not dependent on D-I release schedules!

17 September 2008

Christian Perrier: Slovenian rescued... Macedonian maybe rescued as well..and Catalan complete

After I (on purpose) posted an alarming blog entry yesterday about some languages being "endangered" in Debian Installer, I got two mail exchanges today. One with Vanja Cvelbar, who completed enough in Slovenian translations of D-I for the language to requalify for Lenny. Kudos to Vanja, the Slovenian users owe you a lot (I hope they won't hate you because the translation is bad...:-)) Another with someone from the Macedonian users group who committed self to complete Macedonian translations. So, two languages saved. What will I have to do for saving others? Should I make the promise to run naked all around the next Debconf hacklab or something similar? (I should be careful, though, they could even do it just to see this) So, well, continue to make me happy and saved a few of these languages ! PS: ah, and Jordi completed Catalan as well. So, he will still be allowed to dream about World Domination, now.

16 September 2008

Christian Perrier: No more Danish, Ukrainian, Estonian, Slovenian, Latvian, Bosnian, Macedonian in D-I?

Only four days are left and these languages, as well as Amharic, Northern Sami, Slovenian, Albanian, Tagalog are in very high danger of being disabled in Debian Installer. For Bengali, I still have some hope as someone volunteered to fill in the gap left. Catalan is still missing its 5 miserable strings but I guess I won't have the guts to disable it just because it is missing strings that warn users that the translation could be incomplete (feel free to laugh at this paradox but if you think this is stupid, just also feel free to come and fix that bug or complete the damn translation). I can now confess that we will reach a point where we will have less translations for the installer in Lenny than we had in Etch. I don't see any reason for this to change in four days. And, yes, I call this sad news as we (particularly Frans) did a lot of improvement in D-I to lower down the requirements. PS: for those who wonder why I mention only 7 languages in that post's title, I indeed picked up those I still have a small hope I can wake up someone to complete the work in these last four days.

14 September 2008

Christian Perrier: News from D-I last l10n efforts

There's only one week left for D-I translation updates. I wholeheartedly thank Otavio who agreed for such a long string freeze as it allowed me to do my best to get translations completed. And this is a huge communication effort, considering how easily the translators vanish... 46 languages are now qualified for the release, without discussion. Since my last blog entry, welcome back to Greek, Esperanto, Hungarian, Norwegian Nynorsk, Wolof. There are still uncertainties for 14 languages: Amharic, Bengali, Bosnian, Catalan, Danish, Estonian, Kurdish, Latvian, Macedonian, Northern Sami, Slovenian, Albanian, Tagalog, Ukrainian Again, several of these have *very few missing strings*. In short, if your language is among these 14, there are 6.5 days left (the end of the translation update round is on Saturday 20th midnight UTC). RUSH! What will happen in 6.5 days? I will examine the situation of each of those languages and discuss it with the D-I release managers. On a case by case basis, we will decide together to keep them or not. Etch has 58 supported languages (English included). Lenny currently has 47 that are sure. Will Lenny be the first Debian release ever with *less* supported languages in D-I than the former release? It would give some groung to my claim that Debian translators are currently escaping somewhere else (guess where?).

9 September 2008

Christian Perrier: Good day for D-I l10n

Three days after I posted my last blog entry about it, a great progress was made about translation completeness for D-I. We jumped from 34 languages meeting the release criteria up to 41. Shaking out translators seems to be efficient even though t requires a big investment in time. So, welcome back to Spanish, Indonesian, Georgian, Hebrew, Khmer, Nepali, Simplified Chinese. There are still uncertainties for: Amharic, Bengali, Bosnian, Catalan, Danish, Greek, Esperanto, Estonian, Hungarian, Kurdish, Latvian, Macedonian, Norwegian Nynorsk, Northern Sami, Slovenian, Albanian, Tagalog, Ukrainian, Wolof Several of these have *very few missing strings* (as a matter of example, Catalan is only missing the strings....that warn users that the translation might be incomplete...interesting chicken-and-egg situation which could be easily solved by completing 5 miserable strings). 12 days left (the end of the translation update round is on Saturday 20th midnight UTC)....hurry!

5 September 2008

Christian Perrier: D-I string freeze status

After more than one week of string freeze for Debian Installer, here's the status (I post it daily on debian-boot and debian-i18n mailing lists). 15 days are left before the end of the string freeze 34 Languages meet the release criteria: Arabic, Belarusian, Bulgarian, Czech, German, Dzongkha, Basque, Finnish, French, Galician, Gujarati, Hindi, Croatian, Italian, Japanese, Korean, Lithuanian, Malayalam, Marathi, Norwegian Bokm l, Dutch, Polish, Portuguese, Punjabi, Brazilian Portuguese, Romanian, Russian, Slovak, Swedish, Tamil, Thai, Turkish, Traditional Chinese 27 currently activated Languages *fail* and risk to be disabled et the end of the freeze: Amharic, Bengali, Bosnian, Catalan, Danish, Greek, Esperanto, Spanish, Estonian, Hebrew, Hungarian, Indonesian, Georgian, Khmer, Kurdish, Latvian, Macedonian, Nepali, Norwegian Nynorsk, Northern Sami, Slovenian, Albanian, Tagalog, Ukrainian, Wolof, Simplified Chinese 14 more languages are under work but will probably not make it: Afrikaans, Welsh, Persian, Irish, Armenian, Icelandic, Kazakh, Kannada, Malagasy, Malay, Serbian, Telugu, Urdu, Xhosa In short, this summarizes to "hurry if you don't want your language disappear from D-I"...:-)

Next.

Previous.